Control systems state vector management using co-processing and multiport ram

ABSTRACT

An integrated state vector management system for control systems includes a plurality of co-processors configured to generate and utilize state vector data. The integrated state vector management system further includes state vector module communicatively connected to each of the plurality of co-processors. The state vector module includes a state vector memory containing at least three memory buffers for storing three datasets of state vector data. The state vector module further includes a state vector memory control logic communicatively coupled to the state vector memory. The state vector control logic is configured to provide read and write control to the state vector memory. The state vector memory control logic includes at least a write pointer controller and a read pointer controller.

FIELD OF THE INVENTION

The present invention relates to embedded systems, and more particularly, to a formal state vector management system for control systems that enables parallel co-processing via multiport memory components.

BACKGROUND OF THE INVENTION

Widely-used modern computer systems are multitasking systems, which means that they can execute several applications and processes in parallel. This parallel execution paradigm can be realized via context switching on a processor as well as simultaneous execution on computer systems that have simultaneous-multithreading processors or multiprocessors. This feature of executing several processes in parallel brings the problem of balancing the load of the system, which is currently handled by the operating systems (OS). Operating systems, including ones with time-slice multiplexing kernels, use scheduling algorithms to determine which threads or processes need to be executed at a given time. Since a computer system has limited resources in terms of processing power, only a certain amount of processes can actively execute at a certain time, and the kernel must have the ability to temporarily suspend the execution of a process to allow the execution of another.

A platform developer or vendor will often provide a set of functions and data structures that implement an API (Application Programming Interface) to manage the collection of and access to the data that is functionally equivalent to a state vector. The mathematical state vector is a vector of values that represent physically important parameters describing a system with regard to the control systems' goals and capabilities. The need to coordinate operations of multiple processes and applications often results in significant OS jitter. OS jitter represents undesirable variation in the latency of operating system kernel operations that should otherwise be determinative and predictable, particularly where real-time response is desired. Thus, any timing jitter is highly undesirable to a state vector implementation. While known jitter can be compensated somewhat by (usually expensive) computation, unknown jitter simply leads to errors.

SUMMARY OF THE INVENTION

The purpose and advantages of the below described illustrated embodiments will be set forth in and apparent from the description that follows. Additional advantages of the illustrated embodiments will be realized and attained by the devices, systems and methods particularly pointed out in the written description and claims hereof, as well as from the appended drawings.

To achieve these and other advantages and in accordance with the purpose of the illustrated embodiments, in one aspect, an integrated state vector management system includes a plurality of co-processors configured to generate and utilize state vector data. The integrated state vector management system further includes state vector module communicatively connected to each of the plurality of co-processors. The state vector module includes a state vector memory containing at least three memory buffers for storing three datasets of state vector data. The state vector module further includes a state vector memory control logic communicatively coupled to the state vector memory. The state vector control logic is configured to provide read and write control to the state vector memory. The state vector memory control logic includes at least a write pointer controller and a read pointer controller.

In another aspect an integrated state vector management system includes a plurality of sensors configured to acquire state vector data. The integrated system further includes a plurality of co-processors communicatively coupled to the plurality of sensors. Each of the plurality of co-processors includes a hardware logic configured to control the acquisition of the state vector data and configured to analyze the state vector data. The integrated system also includes a state vector module communicatively connected to each of the plurality of co-processors. The state vector module includes a state vector memory containing at least three memory buffers for storing three datasets of state vector data. The state vector module further includes a state vector memory control logic communicatively coupled to the state vector memory. The state vector control logic is configured to provide read and write control to the state vector memory. The state vector memory control logic includes at least a write pointer controller and a read pointer controller.

BRIEF DESCRIPTION OF THE DRAWINGS

So that those having ordinary skill in the art, to which the present invention pertains, will more readily understand how to employ the novel system and methods of the present certain illustrated embodiments, the embodiments thereof will be described in detail herein-below with reference to the drawings, wherein:

FIG. 1 is a simplified system diagram illustrating a coprocessing relationship in the sub-system architecture which includes a co-processor designed to receive and process acquired data, in accordance with an embodiment of the present invention;

FIG. 2 is a simplified system diagram illustrating a coprocessing relationship in the sub-system architecture which includes a co-processor designed to receive and control the acquisition of large volume of image data received from external sensors, in accordance with an embodiment of the present invention;

FIG. 3 is a system diagram illustrating a physical model of a conventional multicore integrated computer system for processing machine vision data on a mobile platform;

FIG. 4 is a system diagram illustrating a programming model corresponding to the conventional physical model of FIG. 3;

FIG. 5 is a system diagram illustrating a physical model of an integrated computer system for processing machine vision data on a mobile platform implemented as a System-on-Module (SOM) in accordance with an embodiment of the present invention;

FIG. 6 is a system diagram illustrating a programming model corresponding to the physical model of FIG. 5 in accordance with an embodiment of the present invention;

FIG. 7 is a sequence diagram showing a prior art procedure for data acquisition in the execution of a conventional multitasking operating system using the conventional hardware configuration of FIG. 3 and programming model of FIG. 4;

FIG. 8 is a sequence diagram showing the novel approach for data acquisition in the SOM of FIG. 5 that frees an application processor from the workload related to data acquisitions, in accordance with an embodiment of the present invention;

FIG. 9 illustrates a sequence diagram showing interactions between a state vector module and a plurality of co-processing components on a macro level, in accordance with an embodiment of the present invention;

FIG. 10 is a system diagram illustrating the state vector module in accordance with an embodiment of the present invention; and

FIG. 11 illustrates an expanded sequence diagram showing multiple lower-level interactions between the state vector module and a co-processing component, in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION OF CERTAIN EMBODIMENTS

The below described embodiments are directed to a customized architecture of an embedded machine vision system on mobile platforms utilizing System on Chip (SOC) technologies that accurately collects vast amounts of sensor data (inertial, positional and image, radar data), calculates the position and pose of the sensors and system body and distributes this accurately collected sensor and control data to a system of coprocessors located on the SOC. In general, knowledge of the sensor orientation and position in relative time and space is very computationally advantageous to solve the generic machine vision problems existent with moving platforms. The addition of absolute positional knowledge significantly improves capability of the mobile platform. Various embodiments described herein address architectural improvements that enable simpler and more accurate local and global orientation of the mobile platform.

It is to be appreciated that the below described embodiments are not limited in any way to what is shown in the Figures, and instead, can be embodied in various forms, as appreciated by one skilled in the art. Therefore, it is to be understood that any structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis for the claims and as a representation for teaching one skilled in the art to variously employ the certain illustrated embodiments. Furthermore, the terms and phrases used herein are not intended to be limiting but rather to provide an understandable description of the certain illustrated embodiments.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to relating to below illustrated embodiments. Although any methods and materials similar or equivalent to those described herein can also be used in the practice or testing of the below illustrated embodiments, exemplary methods and materials are now described.

It must be noted that as used herein and in the appended claims, the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a stimulus” includes a plurality of such stimuli (and equivalents known to those skilled in the art) and reference to “the signal” includes reference to one or more signals (and equivalents thereof known to those skilled in the art), and so forth.

As used herein, the term “mobile platform” may refer to any vehicle with or without an on-board human pilot. For example, mobile platform may include, but are not limited to, Unmanned Aerial Vehicles (UAVs), fixed-wing UAVs, rovers, walking robots, hovercraft, submersibles, and surface vehicles, gimbaled stabilized sensor platforms and fixed image, radar platforms. The term “mobile platform” is also intended to refer to any portable electronic device such as a cellular telephone, smart phone, tablet computer, virtual reality goggle, or other suitable wireless communication device communicatively coupled to one or more sensors and running any suitable operating system. Any operable combination of the above are also considered a “mobile platform.”

The term “sensor” is used herein in a broad sense and includes any type of physical sensor or controller, such as a GPS receiver, gyroscope, accelerometer, motor controller, as well as a device for measuring temperature, current, voltage, ADC (Analog to Digital Converter), DAC (Digital to Analog Converter), Digital TO, or the like. The term “image sensor” encompasses any type of image capturing device such as a video camera, radar, lidar, FUR (forward looking infrared imaging) sensor, or any combination of such sensors. The term “image sensor” is also inclusive of multi-spectral imagers and groups or arrays of the same or different image capture devices. A sensor may capture information in a series of two or three dimensional arrays. The image sensor may include both active and passive cameras.

As used herein, the term “processor” is to be broadly construed to include any type of embedded processor.

The term “assert” is used herein to refer to pushing a computer value to a physical machine vision system.

Typical machine vision platforms include pluralities of computing elements, operating systems, physical sensors (i.e., image forming sensors, gyros, accelerometers, GPS), application software and actuation controllers. In a nutshell, a machine vision system works by querying the physical sensors at defined intervals, decoding the sensor feedback, estimating where in space the system is and where it is pointing, synchronizing the capture of the image forming data and collecting all of this information in digital memory. Typically, one or more application components perform each step of this data collection. Then the application software typically runs complex routines that take the image and physical sensor data to create an output. Additionally, the active control elements of a vision system mounted on a mobile platform typically need to react to real world disturbances as detected by the wide modality of sensors. These machine vision systems are often challenged by deterministic behavioral needs exhibited by various components of a distributed system. The distributed nature of the system presents several challenges. Typically, there is a digital controller in the system that collects the sensor information and determines how to respond to this information contingent on the tasks the system intends to perform. Additionally, the machine vision system can have a plurality of electro-mechanical actuators that need to be controlled.

Embedded systems have been used to implement various control systems that enable many real-world functional systems. As previously noted, a mathematical state vector is a vector of values that represent physically important parameters describing a system with regard to the control systems' goals and capabilities. Such values may include, but are not limited to, values for the current angular position of the motor, angular acceleration, angular velocity, motor current, rate of change of motor current, motor temperature, switch temperature, physical inertial moments of the motor, etc. Each of these parameters is an element of a formal system state vector. Typically, the state vector represents a state of the system at a particular time instance. Control systems' processors use this state vector to calculate the next desired output state typically in a time controlled manner. Various embodiments of the present invention enable fidelity in the state vector for embedded systems.

Many control systems are implemented as embedded systems with a completely closed operating environment. It is desirable to utilize modern software applications that could offer a plurality of control system functions in the same embedded system, without jeopardizing the control system's functionality. A mobile machine vision platform is particularly taxing with regards to control system complexity combined with the desire to change application processing. Various embodiments of the present invention leverage the capabilities provided by modern hardware and digital technologies to extend the concept of high fidelity state vector management to heterogeneous computing.

Referring now to FIG. 1, there is illustrated a co-processor designed to receive and process acquired inertial and positional data, in accordance with an embodiment of the present invention. In one embodiment, a machine vision system mounted on a mobile platform 100 preferably comprises a conventional multi-core application processing system (partition) 102 which includes logical partitions 104 that have respective customized DATa Collection and Control (DATCC) processor cores 110 and memory areas 108 for programs, such as program 110 p described below. In several embodiments, the processing circuitry shown in FIG. 1 is implemented using SOC with programmable logic components (e.g. field programmable gate array (FPGA), or complex programmable logic device (CPLD)). In another embodiment, data vision processing circuitry 100 is implemented using any number of discrete logic components. In yet another embodiment, data vision processing circuitry 100 is implemented using an application specific integrated circuit (ASIC). It should be noted that application processor logical partition 102 is a conventional IP (intellectual property) component, while IP core 104 is unique and customized.

System 100 illustrated in FIG. 1 includes an application processor logical partition 102 having a computing device's application processor(s) 106, first co-processor logical partition 104 having one DATCC co-processor 110 and a plurality of sensors 120 attached to a single DATCC co-processor 110. Logical partitioning divides hardware resources so that separate DATCC 110, memory areas 108, 110 p and I/O ports 114,116,118 are allocated to the different physical entities. The multi-core processor system 102 may run application codes in the same operating system (OS) and may be scheduled to run a code in parallel, symmetrical multi-processing mode (SMP). In the architecture illustrated in FIG. 1 application processor subsystem 106 is primarily responsible for executing one or more applications.

It is contemplated herein that application processor 106 may communicate with co-processor partition 104 via a set of registers 108, referred to hereinafter as register interface, and/or any other method known in the art. The inter-core communications may be coordinated by safe data exchange mechanisms, such as exist in operating systems (i.e., Linux).

It is noted that a plurality of sensors 120 collect the variety of inertial and positional data related to the mobile platform. In one embodiment, the position, velocity, and angular orientation of the mobile platform may collectively be referred to as state vector parameters. According to an embodiment of the present invention, the state vector parameters are stored in state vector module 112 comprising a protected and managed read-write memory having a plurality of addressable memory locations. In one implementation, state vector module 112 is situated in the reconfigurable memory fabric shared by all elements in the co-processor logical partition 104. State vector memory 112 implemented as protected and managed multi port random access memory (“RAM”) enables concurrent processing from the complete set of processors implemented in a particular mobile platform system. Advantageously, state vector module 112 further includes state management logic to perform state vector management operations for the acquired inertial and positional data. According to an embodiment of the present invention, the state management logic coordinates sharing and updating the acquired inertial and positional data in a concurrent fashion between application processor subsystem 106 and one or more co-processors described below. For example, the state management logic uses separate read and write ports to access the state vector memory. The ports are configured as multiport access to the variety of processing entities with one or more specific functionalities in the mobile platform system. The state management logic selectively determines when active read and write buffers described below can use a triple-buffered RAM instead of a dual-buffered RAM, with the third buffer being reserved for write access by the state management logic when a state vector read is locking memory access, for example, under debug or error conditions.

According to an embodiment of the present invention, the DATCC 110 and other co-processors of the system are assigned time slices by state management logic around which data from state vector module 112 is read and written. The state management logic utilizes one entity write port access and multiple port read access logic. It is noted that various embodiments of the present invention contemplate that the hardware logic of the coprocessors implements these interfaces natively by design. The state management logic is described in greater detail below in conjunction with FIGS. 9-11.

In one embodiment, DATCC co-processor 110 is configured to perform navigation component data acquisitions and system mobility assertion and control functions. In addition, DATCC co-processor 110 may be configured to actively collect auxiliary data to and from other system components, such as motor controller components 220 and INS (Inertial Navigation System) components 228 (described below in conjunction with FIG. 2) for instrument control purposes. For ease of discussion, the term” inertial and positional data” encompasses such auxiliary data (including motor and status data) collected from other integrated components, such as motor controller 220 and INS 228. In one embodiment, DATCC co-processor 110 executes specific microcode instructions contained in a particular DATCC program 110 p. The DATCC interface (described below) to the state vector module 112 is critically important and the state vector module 112 is a mechanism through which data is asserted to devices/sensors and results are stored. As an example, the DATCC co-processor 110 may run a program that writes a torque value to the motor controller 220. The DATCC program reads a specific memory location of the state vector memory, packages the retrieved value into the correct digital stream output and automatically sends this stream to the motor control device 220.

While only a single DATCC co-processor 110 component is shown in FIG. 1 for ease of illustration, alternative embodiments are contemplated in which any number and combination of DATCC co-processors 110 can be coupled to application processor partition 102. This number is of course limited by the size and layout of the integrated circuit used in logical co-processing partition 104. For example, such logical partition 104 on a mobile platform may include more than 10 DATCC co-processors 110 with 10 programs 110 p and ten register interfaces 108 coupled to application processor partition 102. It is noted that in such embodiments the plurality of DATCC processors 110 are situated within SOC fabric (depicted as co-processing partition 104 of sub-system 100) and act to serialize a plurality of signals that are then easily distributed physically within the mobile platform. In an illustrative embodiment, the plurality of control signals communicated between the pluralities of DATCC coprocessors 110 may replace several hundred connections in a conventional mobile platform system with a few serial communications lines. Advantageously, the disclosed architecture simplifies wiring, removes interrupt and serial communications processing from the application processor partition 102 and offers deterministic behavior regardless of implemented application programming.

It is contemplated herein that DATCC co-processor 110 may operate in at least five different modes. In one embodiment these modes may include, but are not limited to, reset, sleep, chirp acquisition, runtime and init modes. The reset and sleep modes are conventional modes well-known in the art. The chirp acquisition mode comprises an operating mode configured to wake up DATCC co-processor 110 from the sleep mode and execute microcode instructions in DATCC program 110 p a single time.

The runtime mode is an operating mode that executes instructions contained in DATCC program 110 p which may be loaded via runtime mode pathway 111. These instructions may include read/write commands from/to state vector module 112 and/or register interface 108. In one embodiment, DATCC program 110 p is configured and operable to acquire inertial and positional data at predetermined collection-time intervals from the variety of sensors 120 mounted on mobile platform system 100. It is noted that DATCC co-processor 110 comprises a component dedicated to data transfers between the sensors 120 and the state vector module 112. Advantageously, DATCC co-processor 106 relieves application processor 106 of having to oversee the mass data transfer and significantly simplifies interrupt handling requirements for application processor 106, without any loss of efficiency, flexibility and/or extendibility. In one exemplary embodiment, the inventors hereof have observed approximately 20-100 fold interrupt reduction and approximately 0.4 Gbit/sec data movement load removal, as compared to application processor workload in conventional machine vision systems.

In one embodiment, the init mode may run an initialization routine (initialization code) which enables application processor 106 to communicate with devices 120 directly in a so-called “pass-through” mode. Initialization code may be generated by a high-level language compiler into the embedded system programming. In one embodiment, there is an initialization path 107 between a memory component storing DATCC code 110 p utilized during runtime mode and application processor 106. The length of the initialization code may be substantial and, in some examples, the initialization code can be similar in length or may even substantially exceed the main code (i.e., DATCC program 110 p). The initialization code may include code used for testing, profiling, debugging, etc. In other words, in an embodiment, DATCC code 110 p should be limited to simple and repetitive data flows performed in runtime operating mode, while the initialization code may include substantially complex initialization, testing and debug interfaces. Such arrangement provides more efficient resource utilization.

Still referring to FIG. 1, the plurality of sensors 120 may be connected to one or more co-processor partitions 104, via a plurality of interfaces 114-118. In various embodiments, sensors 120 may provide and receive digital communication, provide and receive serial communication, provide analog input that needs to be converted to digital format, receive analog output that has been converted from digital format, provide temperature readings, and the like. In one exemplary embodiment, the plurality of interfaces may include bit level interface 118, standard peripheral interface 116 and enhanced peripheral interface 114.

The set of functions in bit-level interface 118 manipulate selected ones of the transmitted bits, based on the type of the external sensor 120. Bit-level interface hardware dataflow is generally understood by those skilled in the art. For example, bit-level interface standard has been provided with the XC6200 series FPGA from XILINX.

Examples of well-known in the art standard peripheral interfaces 116 may include but not limited to IEEE1394, also referred to as FireWire, Universal Serial Bus, commonly referred to as USB, SPI (Serial Peripheral Interface), UART (Universal Asynchronous Receiver/Transmitter) and the like.

At least some of sensors 120 may utilize enhanced peripheral interface 114. This type of serial communication is typically high speed, low power and may be converted to the device specific interface at a particular sensor 120. Enhanced peripheral interfaces 114 typically allow minimizing pincount and power consumption and providing power/signal isolation and timing skew compensation for synchronous serial interfaces.

FIG. 2 is a simplified system diagram illustrating a coprocessing relationship in the sub-system architecture which includes a co-processor designed to receive and control the acquisition of large volume of image data received from external sensors, in accordance with an embodiment of the present invention. System 100 illustrated in FIG. 2 includes an application processor logical partition 102 having a computing device's application processor(s) 106, second co-processor logical partition 203 having one or more customized co-processors and a second plurality of sensors 202 attached to second co-processor partition 203. In several embodiments, various circuitry components shown in FIG. 2 may also be implemented using FPGAs, CPLDs, ASICs and/or any number of discrete logic components. It is contemplated that in the illustrated embodiment, register interface 108 utilized for inter-partition communication is disposed within the application processor partition 102.

In a number of embodiments, the second plurality of sensors 202 attached to second co-processor partition 203 comprises image sensors such as cameras 202 a and 202 b, which may be configured to transmit image data via an interface format. The captured image data is transmitted in accordance with the interface format as a stream or packet. These streams can be adapted to accord with any interface format, including but not limited to the Mobile Industry Processor Interface Alliance (MIPI) CSI-2 interface format (MIPI interface format), CameraLink interface format, a USB interface format, or a Firewire interface format.

In accordance with an embodiment of the present invention, the co-processor partition 203 includes one or more co-processors 206, referred to hereinafter as DATCAP co-processors, configured and operational to perform ingestion of high-bandwidth image data in a substantially standard manner. In an embodiment of the present invention, each of the DATCAP co-processors 206 is communicatively coupled to each of the second plurality of sensors 202. Furthermore, DATCAP co-processor 206 is coupled with state vector module 112 comprising the state management module 112 described herein. As shown in FIG. 2, in some embodiments, image data received from the devices 202 may be converted by bit-level interface 204 into appropriate format. In several embodiments, image data from the plurality of cameras 202 a-202 b can be packetized by DATCAP 206 by inserting the image data and/or additional data describing the image data into a packet in such a way that application processor 106 can reconstruct images of a scene from the received image data and utilize additional system information related to the reconstructed images. This process of insertion of additional data describing the image data transmitted by cameras 202 is referred to hereinafter as metatagging. This additional data is provided by the state vector module 112 and one exemplary application of this data is described below. The image is typically rectangular and has four corners and corresponds to an image space and its projection onto the Earth. Examples of metadata inserted by DATCAP 206 include, without limitation, earth coordinate positions of a location at which the image was taken, data indicating the geo-location coordinates for the points in the Earth-Centered Earth-Fixed and/or north/east/down coordinate system corresponding to the four corners of the image and one or more timestamps (e.g., timestamps from GPS, timestamps from the machine vision system) indicating when an image was taken (e.g., date and time), information indicating whether the mobile platform was accurately stabilized at the time the image was taken, any detected error conditions, and the like.

It is noted that metatagging performed by DATCAP co-processor 206 and state management logic (state vector module 112) rather than by application processor 106 makes the process highly accurate. Furthermore, this embodiment of the present invention provides a way to perform metatagging by a dedicated co-processor thus neglecting effects of jitter induced by operating system scheduling or other specific programming and/or multithreaded conflicts and thus allowing both high performance and optimal accuracy without the expense and error of software based synchronization. Since each DATCAP processor 206 is a separate physical instance (entity) in the chip, the disclosed architecture easily scales to multiple sensors with complex and varied timing requirements. In one embodiment, the metatags inserted by DATCAP co-processor 206 include data that may be used to provide additional information for an image/data processing function later in the processing pipeline in a parallel fashion. In one embodiment, DATCAP co-processor 206 may achieve this by copying the needed metatags into the data stream of image data received from sensors 202 and by utilizing customized hardware logic for the data localization needed for parallel processing.

Still referring to FIG. 2, it is noted that the size of the data flow (i.e., video, LIDAR, camera data) ingested by several complex DATCAP co-processors 206 precludes the use of the state vector multiport memory buffers for storage due to technical limitations (i.e., size of the on-chip memory in state vector module 112). According to an embodiment of the present invention, the computing system shown in FIG. 2 further includes multiple physically separate arrays (banks) of relatively large off chip memory. In various embodiments this memory may comprise at least one of flash memory, dynamic random access memory (DRAM), 4×DDR (dual data rate) memory, or the like. With respect to application processor 106, it is noted that the application processor's operating system 106 is communicatively coupled to a physically separate block of off chip storage 214 a. The application processor 106 might run a conventional operating system (e.g., Linux) and may use a variety of memory management components, including, but not limited to, standard cache, DDR controllers 212 a, Linux memory management, thread context, multicore memory management. According to various embodiments, the mobile platform described herein may utilize a plurality of other large off chip memory systems. Advantageously, this approach enables movements of large items of data to and from various memory components without application processor's 106 involvement and helps to avoid various typical OS constrained memory conflicts. For simplicity of discussion and illustration, these multiple banks of memory utilized for storage of machine vision data are referred to hereinafter as DDR banks 214.

Various embodiments of the present invention utilize separate DDR arrays 214 b that are directly controlled and scheduled by a plurality of DDR controllers 212 b also included in second co-processor logical partition 203. As illustrated in FIG. 2, the movement of data from the DATCAP 206 is bifurcated offering two distinct paths. One path is to a particular DDR controller 212 b via the memory controller 208 that controls routing of data to the variety of programmable memory locations with available DDR banks (bank is combination of 212 and 214). In addition, the memory controller 208 also controls a plurality of image processing pipeline components 209 where metatagged data is pipelined from stage to stage in the image processing pipeline flow, according to an embodiment of the present invention. The memory controller 208 prefetches data for the image processing pipeline components 209 from the DDR locations 214 b via a corresponding DDR controller 212 and loads “lines or strides” of auxiliary data needed by the image processing components 209 for the pipeline in addition to the image data originating from the DATCAP 206. In an embodiment of the present invention, a stride may comprise a row of pixels of a corresponding image. The image processing components 209 perform complex mathematical manipulation of this large size ingested data in a power efficient, deterministic manner.

According to an embodiment of the present invention, the image processing components 209 may perform large computations that rely on positional and multimodal data for a plurality of conventional calibration, alignment and projection functions that are typically performed by machine vision systems. Non-limiting examples of such functions include, NUC (non-uniformity corrections), homographic affine projection of data, Lidar data binning, histogramming, aligning data functions and the like. Some of these functions are large and/or complex with regard to data movement scale and data correction while other functions are computationally expensive, difficult to program due to large interrupt count and requirements of deterministic behavior for control and measurement accuracy. These novel image processing components 209 are not general purpose and offer interfaces and programmability that are specific to tasks present in various machine vision applications and interfaces for moving platforms that work cooperatively on a single chip and that offer basic functions needed for these applications in a power and space efficient manner.

In an embodiment of the present invention, DDR controllers 212 are operable and enabled to schedule access to a variety of DDR memory arrays 214 using the memory controller 208. This type of arrangement allows DATCAP co-processor 206 to stream data to DDR banks 214 without burdening the application processor 106 with any substantial involvement. As previously noted, DATCAP co-processors 206 also have access to the state vector module 112. Advantageously, the hardware arrangement illustrated in FIG. 2 enables DATCAP co-processors 206 to synchronize image data deterministically with the state vector data and store this synchronized machine vision data deterministically to DDR arrays 214 b and/or feed the synchronized data to the image processing components 209. Various embodiments of the present invention contemplate that DATCAP co-processors 206 are configured to store the state vector data aligned with the large size image data in convenient chunks, making it easy to gather, record and send complete system states of machine vision system to any digital device. Furthermore, DATCAP co-processors 206 offload metatagging and data capture and movement tasks from application processor 106, thus relieving application processor's 106 workload and bandwidth.

According to an embodiment of the present invention, DATCAP co-processors 206 may be communicatively coupled to capture sequencer component 210. The capture sequencer component 210 may be configured to sequence the image data based at least in part on state vector values and/or other control signals (i.e., control signals provided by application processor 106 via register interface 108).

Advantageously, the system state vector management logic of the state vector module 112 is constructed in a customized memory implementation and provides defined, deterministic performance with respect to update and query of data contained in state vector module 112. In one embodiment, DATCAP co-processors 206 receive state vector data from state vector module 112 using safe/non-blocking memory asserts. Advantageously, the state vector memory of the state vector module 112 is designed to be both multi-ported and non-blocking. Consistency of the state vector is defined by an immutable copy of the state vector data that is not corrupted by the parallel update mechanisms during system use of each data element. Consistency means that all system elements have access to the same immutable copy of the state vector data simultaneously without blocking behavior. In other words, DATCAP co-processors 206 or any other component of digital logic partition 203 can simply query the update value of any state vector memory location with consistent, deterministic performance. Furthermore, the illustrative embodiment depicted in FIG. 2 also places the sensor interface complexity into the customized logical partition 203 thus freeing up the application processor 106 from the burden of computing it had previously done. As a result, application processor 106 no longer needs to handle interrupts related to various device interfaces as illustrated in FIG. 8 below. This greatly simplifies the programming model and simplifies the creation of robust device library (API) for all of the sensors (devices) on a mobile machine vision platform.

The memory controllers 208 depicted in FIG. 2 may comprise digital circuits that manage the flow of image data going between DDR arrays 214 and DATCAP coprocessors 206, image processing pipeline elements 209, the Ethernet routing component 224 and application processor's memory controller 211. In various embodiments, memory controllers 208 enable data streaming to various image processing components 209 and/or enable direct storage of image processing results to DDR SRAM arrays 214 b as described above.

Advantageously, in various embodiments, memory controller 208 may be programmed to meet application specific needs, dependent on specific image data provided by the second plurality of sensors (i.e., image sensors) 202 and dependent on data processing steps allocated to the hardware logic of image processing components 209. For example, it is contemplated that a mobile platform is typically an integrated platform with known types of fixed cameras and IMU (Inertial Measurement Unit) instruments as well as known calibration needs and software modules. In some embodiments, memory controllers 208 can also be programmed via a script that organizes DDR partitioning and data access sequences needed by the DATCAP coprocessors 206.

Thus, according to an embodiment of the present invention, with respect to the collection of large volume image data (which may include lidar and radar data) from the second plurality of sensors 202 each DATCAP co-processor 206 is controlled via capture sequencer 210. The capture sequencer 210 is communicatively connected in turn to the state management logic of the state vector module 210 which controls the capture sequencer 210 with bit level values in registers. The capture sequencer 210 and the plurality of DATCAP co-processors 206 connect to memory controllers 208. According to an embodiment of the present invention, each DATCAP co-processor 206 is connected to a single memory controller 208. In one embodiment, capture sequencer 210 and the plurality of DATCAP co-processors 206 send signals related to trigger information (described below) to memory controllers 208. As previously indicated, DATCAP coprocessors 206 are connected to the state vector component 112, perform metatagging described above and route the metatagged data to corresponding memory locations as defined by memory controller 208. The memory controller 208, in turn, sends the metatagged machine vision data to a particular DDR array 214 b.

Still referring to FIG. 2, digital logic partition 203 may further include one or more co-processing components 216 configured to offload computational tasks associated with pointing a particular image sensor 202 at a desired location in an active mobile platform system while guiding the system geometry to a desired location along a desired path. Collectively, these calculations related to desired system path and desired pointing location and conversion to DCM (discrete cosine matrices) and motion profile calculations for sensor pointing comprise a task called pointing. This computationally expensive task needs to be updated very regularly and precisely and relies completely on a plurality of the state vector parameters. It is noted that the results of the pointing calculations are placed back into the state vector and utilized by the motor control systems 220. In accordance with an embodiment of the present invention, pointing calculations are performed by the pointing coprocessor 226. In other words, the pointing coprocessor 226 calculates and updates DCM and trajectories for the motor controllers 220 to follow. It is noted that the pointing processor 226 is typically given a target location, line or spline to follow by the application processor 106 via the state vector module 112. According to an embodiment of the present invention, the pointing coprocessor 226 can perform the above-described tasks without any oversight of application processor 106.

In one embodiment, gyro/accelerometer interface 222 is configured to process output of a plurality of gyroscope/acceleration sensors. Accelerometers may be used to sense acceleration of the mobile platform they are attached to (e.g., gravity, sudden starts/stops, motion induced variance). The gyro sensors measure the rate of rotation. Gyro/accelerometer interface 222 may be either an analog, pulse-width modulated (PWM), or digital interface. The gyro/accelerometer sensors are preferably placed on one of the moving components of the mobile platform and coupled to the system based on the actual current location and rotation of the sensor in the system at the time of measurement. This complicated timing relationship and accurate update timing is a major source of system errors which may compound geometrically. For example, the coupling of one axis to the next creates compounding inverse DCM derotation of each axis in a gimbal of computerized multilink arm or rotation of a vehicle bound or human worn system while trying to resolve where a particular sensor is located and pointing to (6 degrees of freedom) in a 3D space. The integral of rate cross acceleration sensors offer this 6 DoF (6 degrees of freedom) calculation when a starting position is known. The fidelity and drift of the sensors clearly affect outcome as does the correctness of the simultaneous state acquisitions of the system. In various embodiments, the Gyro/Accelerometer interface 222 combines multiple inputs from a potential variety of system gyro and accelerometers, and encoder data to perform Kalman filtering to make better estimations. It is noted that gyro/accelerometer coprocessor 222 also relies on the state vector module 112 for data input and output.

The purpose of an INS component 228 is to compute and provide a navigation solution to a machine vision mobile platform on which it is installed. A navigation solution consists of the Position, Velocity and Attitude (PVA) and Roll Pitch Yaw of the INS 228 with respect to the Earth. INS component 228 computes a navigation solution based on the dead-reckoning principle: given the initial position, velocity and altitude of the mobile platform (referred to as “initial conditions”), continuous readings from the devices (i.e., sensors) 120 of the platform are used to keep an updated navigation solution even and particularly when the platform is in a dynamical (rotating) state. Errors in the dead reckoning approach can be mitigated by Kalman filtering techniques that utilize GPS position updates. INS component 228 preferably is directly coupled to state vector module 112 and may utilize the state vector module 112 as an input and output buffer interface. It is noted that application processor 106 asserts several other navigation control and data states to INS component 228 through registers interface 108, for example.

In accordance with an embodiment of the present invention, motor control interface 220 is disposed within the digital logic partition 203 and communicates with the first plurality of sensors 120 (shown in FIG. 1) via DATCC interface 110 and via the state vector module 112. Motor control interface 220 may ingest both positional and motor state data directly from the state vector module 112. It is noted that a conventional system with an external motor controller acts differently. The motor controller is generally self-sufficient. In other words, typically, positional data for the axis being controlled is ingested by the motor controller directly. Normally, the motor controller measures real time torque, current, voltage and interprets serial or analog commands from the application processor 106. The motor controller generally ingests encoder/sensor data directly and then the application system (i.e., application processor 106) must periodically query the motor controller via a command and response mechanism. The non-deterministic response of many motor controllers to a query by the application processor 106 is very disadvantageous with significant performance impact and significant latency substantially guaranteed.

Advantageously, various embodiments of the present invention contemplate that motor control interface 220 preferably ingests the sensor/encoder data directly, via a DATCC co-processor 110 and the state vector parameter sharing that converts the ingested data into an appropriate format, calculates velocity, acceleration, coil currents, coil voltages, inertial data and positional information of an axis, then updates a Kalman filter to estimate local parameters and stores the calculated data in the state vector module 112. Based on trajectory parameters and distance to a particular target in an axis calculated by the pointing processor 226 or application processor 106 the motor controller 220 continues to calculate current output phase and amplitude to drive a motor along it trajectory towards its destination. It is emphasized that, just like other co-processing components 216, the motor control interface 220 utilizes the state vector module 112 for storing generated data. Ethernet processing offload components may include Ethernet routing unit 224 and an Ethernet computation unit 230 which will be described in greater detail below in conjunction with FIG. 5.

Advantageously, the configuration illustrated in FIG. 2 of a plurality of DATCAP coprocessors 206, separate memory controller(s) 208 and separate physical memory, such as DDR memory 214 act to offload a plurality of data moving functions from the application processor 106. These data moving functions relate to movement of the acquired image data. Further, a novel system architecture disclosed herein provides these complex data moving functions as a system service allowing a user of the platform the ability to write software in the application processor space using common techniques where preprocessed, properly (accurately and deterministically) metatagged data is available. Of paramount importance to a mobile machine vision system is the positional knowledge and direction and/or stabilization of where a sensor is placed and oriented in space (both position and pose), various calculations with simultaneous motor axis control and the accurate knowledge of sensor input timing, as well as very accurate matching of image data to the position and pose data over the various data collection periods.

FIG. 3 is a system diagram illustrating a physical model of a conventional multicore integrated computer system for processing machine vision data on a mobile platform. As shown in FIG. 3, in this implementation a plurality of devices 120 common to a mobile machine vision platform such as, but not limited to, gyroscopes, accelerometers, motors, encoders, GPS devices are communicatively coupled to a single integrated circuit 302 via interface electronics 324, such as bit-level interface, for example. This bit level interface converts signals in a manner compatible with standard microprocessor peripheral interfaces, such as UART-based 310, SPI-based 312, I/O or similar interfaces.

The integrated circuit 302 may comprise a multi-core processor having a plurality of processors 304 and having an integrated level 1 (L1) cache and level 2 (L2) cache 306. The entire processor subsystem illustrated in FIG. 3 maps to elements 102 in FIGS. 1 and 2. In other words, the application coprocessor system 106 in FIGS. 1 and 2 is shown in FIG. 3 as elements 304,306, 308, 310 and 314 described herein. A multicore system 300, illustrated in FIG. 3 merely for comparison purposes, runs an operating system and thus is subject to very strict rules of threading, scheduling and sharing data and memory access, including compliance with established programming concepts and assumptions. Various components of the integrated circuit 302 are interconnected by a bus interconnect, which falls under the broader umbrella of an “on-chip interconnect” (e.g., crossbar interconnects and the like), such as AXI 308.

Integrated circuit 302 also includes a (UART) 310, SPI interface 312 and Ethernet interface 330. All devices 120 are connected through any of shown interfaces 310, 312, 314. The high data rate sensors, such as image sensors 202, are connected to the high speed AXI data bus 308 via digital IO 314 that enables streaming of image data to system's memory, such as DDR 214 a. It is noted that different types of image sensors 202 may have different physical interfaces typically configured to convert acquired image data into a digital datastream transmitted to the AXI bus 308.

Relying on this conventional system architecture the running operating system must ensure to provide a portion of the compute time to each asynchronous task/interruption coming from every sensor 120 thru any peripheral interface 310 312, 314 and 330. The operating system also must allocate memory access to a monolithic memory system (OS typically only sees one big block of DDR 214 a) for each small memory update to a state vector. During this memory access organization and access grant condition, the OS must typically interrupt computations performed by other threads, causing large amount of memory churn and creating L1 and L2 cache 306 “misses” on these context switches. These interrupts may occur at rates of ten thousand per second. Accordingly, such context switches and interruptions are computationally expensive and can consume the entirety of the CPU resources just in data acquisition. The programming model of this exemplary conventional system is shown in FIG. 4.

FIG. 4 is a system diagram illustrating a programming model corresponding to the conventional physical model of FIG. 3. As illustrated in FIG. 4, programming model 400 is categorized into different layers. The hardware platform layer 401 of integrated circuit 302 specifies the physical attributes of the chip 302 such as physical peripheral interfaces 310-316, these peripheral interfaces are typically communicated with via a device driver abstraction 404, a file I/O abstraction 403 or a socket abstraction 405. The application code running in the application layer 402 of the operating system 414 can only interface with the abstraction offered in components 403-405. The operating system 414 operates based on the states presented in the listed abstraction layer elements 403-405. The operating system 414 allocates slices of computing time via the abstraction layer elements 403-405 and provides interrupt handling to implement various system functions. It is noted that typically the operating system 414 operates based on somewhat generic rules of prioritization and scheduling and based on somewhat strict rules with respect to memory coherence between various threads. Thus, in conventional computer systems, the operating system 414 plays a central role in the overall system performance. However, in conventional mobile platforms several performance chokepoints arise in that a single memory system 430 is used with heavy performance penalties being applied by the rapid interrupt demands typical of various mobile vision platforms.

One or more applications 402 may call any application programming interface (API) 406, device driver 404, socket 405, asynchronous file IO interface 410, daemon service 412 and may be able to access a direct memory access (DMA) buffer 408. Daemon services 412 are programs that run continuously or in the background and handle periodic service requests received by application 402 and add more complexity to interrupt latency and determinism variance. At the next layer, operating system 414 may utilize a plurality of device drivers 404, files 403 and network sockets 405. It is noted that each thread calling each interface creates a schedulable event in the OS 414 that needs to be serviced. Furthermore, each interrupt trapped by the OS 414 needs to be assigned to a software callback function attached to a particular thread that needs to be scheduled to act on the new data presented to the system. This architectural approach leads to a fairly large number of resource sharing conflicts between all sensors and interrupts competing for processing time, thus affecting timely updates of state vector information. Even slight timing variations in input interrupts can lead to chaotic behavior of the entire mobile platform.

It is noted that illustrative programming model 400 depicted in FIG. 4 contemplates that state vector information 413 utilized by various components of the mobile machine vision platform is stored in the shared memory 430 along with other types of information such as, but not limited to OS data 414, application code 418, image, LIDAR and map data 416, thread execution context 420 and thread local storage 422.

As the operating system 414 must react to various memory location updates happening essentially simultaneously and asynchronously, the memory controller is very busy swapping out thread contexts and substantially constantly refreshing cache as the data accesses are all over the memory space typically causing great conflicts between multiple threads attempting to write to the single memory space 430 managed by the operating system 414. This bottleneck worsens in a multicore system as more cores are added and as memory coherency is further challenged. It is noted that the programming model illustrated in FIG. 4 is completely dependent on the application processing implementation details and the numerous specific details related to operating system functions, individual device drivers and individual sensors.

FIG. 5 is a system diagram illustrating a physical model of an integrated computer system for processing machine vision data on a mobile platform implemented as a System-on-Module (SOM) 500 in accordance with an embodiment of the present invention. In one embodiment, SOM 500 may include a plurality of partitions, such as a first (e.g., CPU) partition 501 a and a second (e.g., FPGA, digital logic) partition 501 b. As shown in FIG. 5, in this implementation a first plurality of devices 120 such as, but not limited to, gyroscopes, accelerometers, motors, encoders, GPS devices are communicatively coupled to one or more DATCC enhanced peripheral interfaces 114 which are in turn coupled to one or more DATCC coprocessors 110. A specific implementation of a DATCC is contained in the functionality of SPI management system and is further described in co-pending application Ser. No. 14/461,086 incorporated by reference herein.

As shown in FIG. 5, components of the first partition 501 a in the present embodiment have substantially the same configuration as the integrated circuit 302 of a conventional embedded system (shown in FIG. 3). Therefore components identical or similar to those of the conventional integrated circuit 302 will not be described again. With respect to the second partition, advantageously, in this embodiment the state vector module 112 may be implemented in hardware as an integrated system of components and interfaces. In one embodiment, the state vector module 112 may include a block random access memory (BRAM) 526, a State Vector (SV) controller 520 and a plurality of SV interfaces 522 that communicatively connect to each co-processing component interface (e.g., INS 228) that accesses state vector information. It is noted that other co-processing components (not shown in FIG. 5) within second partition 501 b may have similar interfaces to the state vector module 112. In one embodiment, BRAM 526 comprises a multiport memory that stores and distributes the system parameters (i.e., state vector parameters) at rates in excess of the physical measurements typically available in conventional mobile platforms. The state vector controller 520 is configured to operate without the oversight of application processor 106. However, it is noted that state management logic included in the state vector module 112 is capable of communicating with a device driver in the application processor's 106 operating system to provide the application processor 106 access to the state vector data (read/write) in a low (substantially zero) overhead and in a safe, non-blocking manner. Advantageously, the state management logic also provides all other co-processors (such as DATCC co-processors 110, DATCAP co-processors 206, navigation co-processors, etc.) the same non-blocking, high performance behavior. DATCAP co-processor(s) 206 receive data provided, for example, by the second plurality of sensors, such as LIDAR devices 202 b. In some embodiments inter-partition communication may be performed via FPGA interface 516. It is noted that at least in some embodiments, different sets of DDR arrays (214 a and 214 b, respectively) may be associated with each partition. The information may be routed to an appropriate DDR block 214 by one of the memory controllers 208 and 211.

As previously indicated, the first plurality of sensors 120 communicates via enhanced peripherals interface 114 with DATCC processor(s) 110 that handle high frequency interrupt low bandwidth inertial, positional and auxiliary data and provide updates to the state vector module 112 using the SV interfaces 522. The second plurality of sensors (i.e., image sensors 202 a and 202 b) are ingesting high bandwidth image data using DATCAP components 530 that comprise bit-level interfaces 204 and DATCAP coprocessors 206. The DATCAP components 530 offer the aforementioned metatagging services via SV interfaces 522. The DATCAP components 530 interact directly with image processing pipeline components 209 described above in conjunction with FIG. 2. Memory Controller 208 is configured to route tap points from the image processing pipeline components 209 to various DDR memory locations 214 b. A tap is an analysis point within a set of received image data. The first pipeline tap point is equivalent to routing raw data from the image forming sensor input.

In addition, various embodiments of the present invention contemplate utilization of Ethernet protocol as a communicative medium between the SOM 500 and various external components, as well as internal communicative medium within the digital logic partition 501 b. Accordingly, SOM 500 may further include embedded Ethernet traffic offload engine comprising a routing element 224 and memory controller 208.

It is highly desirable for the application processor 106 and the application processor partition 102 running an OS to have access to a standard internet connection. Such internet connection enables the application processor 106 to support all of the standard features of an advanced operating system. The variety of standard services include, but are not limited to, very large SSL (Secure Socket Layer), telnet, FTP (File Transfer Protocol), rsync, DHCP (Dynamic Host Configuration Protocol), ARP (Address Resolution Protocol), HTTP (Hypertext Transfer Protocol), etc. These network services run as daemons 412 (or equivalent) and are loaded by the application processor 106. While simply connecting the Ethernet network to corresponding processor's interfaces enables these network services in a conventional mobile platform system, a serious problem may arise when the mobile platform system is asked to move large amount of image data using the same Ethernet connection 516. Such data transfer request forces the conventional mobile platform to use the operating system 414 for copying packet data from its controlled DDR memory 214, assembling packets of data and transmitting them to the Ethernet port 516 on a timed schedule. While utilization of the advanced DMA and AXI facilities reduces the load, but the resource consumption of the mobile platform typically remains to be very large. A similar condition arises when an external component wishes to send large amount of data to the SOM 500. Furthermore, it is highly desirable to route large data sets to various memory systems controlled illustrated in FIG. 5 from external sources. An embodiment of the present invention makes it possible to use the port number of a service to route the Ethernet packets to either the application processor partition 501 a or the digital logic partition 501 b. In addition, it is highly desirable for the application processor 106 to control the transfer of large bandwidth data (i.e. image data) from the digital logic partition 501 b to one or more external IP addresses.

In view of the above, various embodiments of the present invention contemplate that Ethernet router 224 has four primary functions. These functions include: (1) routing Ethernet packets to the application processor 106 based on an input packet's source IP address, destination IP address and port number; (2) routing Ethernet packets from the application processor 106 to the external component based on the destination and source IP addresses and port number information; (3) routing Ethernet packet data to the digital logic partition's 501 b memory based on input packet's source and destination IP addresses, port number and a customized header placed in each Ethernet packet; (4) routing various data blocks placed in DDR memory arrays 214 b to destination IP addresses and port numbers, wherein the source data memory locations should be programmable by the application processor 106. These implementation goals provide a complete Ethernet stack to the SOM 500, while simultaneously providing SOM 500 ability to route data from the digital logic partition 501 b to a plurality of destination IP addresses without application processor's 106 overhead.

According to an illustrative embodiment of the present invention, SOM 500 appears to be a standard Ethernet connection to the application processor 106 and various external network devices, but offers an API (e.g., function calls via the FPGA interface 516) enabling the application processor 106 to identify a target memory location and data size in the digital logic partition's DDR array memory space 214 b that can be transmitted via Ethernet network to any IP address desirably by the application processor 106. Furthermore, the aforementioned API can configure this transmission to happen automatically based on a particular capture sequencer 210 event. More specifically, according to an embodiment of the present invention, the entire SOM 500 can be considered as having one IP address, for example, IPbase.

In addition, the Ethernet router 224 is extended to enable the use of standard sockets for the Application processor 106. The Ethernet router 224 decodes packets addressed to reach the application processor 106 and reconstructs the packets to redirect them to the Ethernet controller 531, as expected by the OS 414 implementing basic socket connections. The Ethernet router 224 then spoofs the IP connection at a signal level and effectively requires no changes to any standard socket behavior (except for port being mapped to digital logic partition 501 b) performed by the application processor's OS 414. The Ethernet router 224 maintains a list of ports with targeted destinations in the digital logic partition 501 b for which it will process packets. This novel feature provides the SOM 500 complete Ethernet compliance.

According to an embodiment of the present invention, incoming packets targeted at memory locations in the DDR arrays 214 b are handled differently by the Ethernet router 224. In these cases, the Ethernet router 224 first evaluates the input packet's source and destination IP addresses and port numbers, then decodes the packet header to determine digital I/O bank, requested memory location and total transfer size. Next, the Ethernet router 224 verifies validity of the received packet and may use any suitable encryption technique. If the Ethernet router 224 is satisfied with the packet validity, it next buffers the packet data and sends a transfer request to the DDR arrays 214 b via the memory controller 208. In response to the received request, the memory controller 208 transfers the payload data included in the packet to the digital logic partition's DDR memory space 214 b. This achieves the above specified function of Ethernet router 224 directed to data transfer into digital logic's 501 b memory space 214 b without application processor's 106 overhead.

The Ethernet router's 224 function of data transfer from digital logic partition's 501 b memory space 214 b to external Ethernet ports without application processor's 106 overhead can be implemented as follows. It is noted that the application processor 106 usually configures the capture sequencer component 210 that triggers image data acquisitions based on timers and/or state vector status information. It is further noted that application processor's 106 is aware of image processing pipeline 209 configurations, of current image processing tap and its mapping to digital logic's 501 b memory location 214 b. Thus, a timestamp corresponding to a particular instance in time when new image data is available in digital logic's 501 b data space is known and entered as a capture event offset in the capture sequencer 210. The application processor 106 can define the event that triggers the automated data movement and the particular memory location, data size and the destination IP for the packets. In one embodiment, these parameters can be communicated to the Ethernet router 224, via the application processor's 106 API function call. The trigger event follows the capture sequencer's 210 event and the Ethernet router 224 sends a data transfer request to the memory controller 208 identifying the memory blocks that need to be retrieved. The Ethernet router 224 typically requests substantially large memory blocks and immediately transmits them to the Ethernet controller 531 facing external Ethernet network. This exemplary embodiment provides an advantageous approach to meeting the above specified function of Ethernet router 224 with near zero overhead placed on application processor 106 with respect to large data transfer. Similarly, an exemplary embodiment of the present invention provides an ability to send state vector data using an IP port by merely providing a separate API function for sending the state vector data.

Generally, the internal fabric of the digital logic partition 501 b is much faster than the Ethernet's baud rate, however, the Ethernet router 224 does need to schedule access with the asynchronous nature of messaging events. According to an embodiment of the present invention, the Ethernet router 224 may implement a simple scheduler and a first-in-first-out (FIFO) buffer of packet I/O for various interfaces. For example, the Ethernet router 224 can create two FIFO buffers per each interface (input and output) for the application processor 106, the digital logic 501 b, and the state vector interface 522. In one embodiment, these buffers can be implemented in BRAM 526 and can have a size substantially equivalent to the size of few large data packets (e.g., 6 Kbytes).

To reiterate, various embodiments of the present invention contemplate utilization of Ethernet protocol as an internal and external communicative medium for SOM 500. In an embodiment, Ethernet router 224 interacts with various reconfigurable system memory controller components described above. It is contemplated that one or more applications executed by application partition 102 could request the Ethernet controller 531 to transfer a block of memory data from memory 214 b to the Ethernet port 316 by adding corresponding header and CRC information to a corresponding request. Thus, effectively the disclosed architecture enables the application processor 106 to stream large data flows to Ethernet 316 with negligible processing load on the application processor 106. Using predefined ports and commands from the application processor 106, the Ethernet controller 531 can stream data from the separate RAM in the reconfigurable system to the network. Advantageously, the state vector controller 520 also can stream data directly to an Ethernet network using the Ethernet controller 531 without processing overhead of application processor 106, yielding fidelity and deep debug capability. In various embodiments, SOM 500 may include a plurality of Ethernet controllers 531 and Ethernet routers 224 thus providing separation of data streaming capability to multiple Ethernet connections 516. Advantageously, the disclosed architecture is capable of reducing application processor's 106 load at least 100× using modern SOC FPGA/ARM processing components.

FIG. 6 is a system diagram illustrating a programming model corresponding to the physical model of FIG. 5 in accordance with an embodiment of the present invention. As illustrated in FIG. 6, programming model 600 is categorized into different layers. The hardware platform layer 601 of SOM 500 includes embedded state vector module 112 communicatively coupled to a plurality of interfaces. In this embodiment all components of the hardware platform layer 601 are configurable and commanded via device driver 404. Also, in the arrangement illustrated in FIG. 6, LIDAR data and image data are preferably stored in a dedicated external memory portion 430 b, separately from application and OS level data. It is noted that embedded state vector module 112 significantly reduces application processor's 106 load, improves performance of the system as well as accuracy of the collected measurements. DATCC 110 and DATCAP 206 represent co-processors shown in FIGS. 1 and. 2, respectively, wherein DATCC 110 comprises hardware logic configured to collect input data and control output data by running its own program 110 p described above and DATCAP 206 comprises hardware logic configured to perform ingestion of high-bandwidth image data from a streaming data source without application processor's 106 overhead by utilizing data capture sequencer 210 and memory controller 208. Major workloads of image processing are implemented in the image processing pipeline components 209. The application processor 106 can configure and load a program for the coprocessing entity using the device driver 404. Such programs may include a DATCC program 110 p, the configuration for a DATCAP 206 (e.g., a specific parameter file) and a sequencer configuration parameter set for capture sequencer component 210. The memory controller 211 is also configured with a memory access table and schedule that ensures efficient memory accesses. Likewise the Ethernet router 224 can be configured with a parameter set via an API function communicated through a device driver 404. The INS 228, Pointing 226, Gyro interface 222 and Motor Control 220 co-processing components (shown in FIG. 2) may utilize conventional fixed function interfaces with a parameter table and status bits. The status bits for these co-processing components are used by the application processor 106 to monitor system's health and require very little oversight.

The availability of the state vector data to the application processor 106 can also be utilized to monitor system state but usually has no critical timing requirements. Essentially, the application processor 106 configures the plurality of coprocessors, starts them, then merely controls macro events and monitors the overall status of the mobile platform. The advantages of the disclosed architecture are further discussed by considering how interrupts are removed from the application processing interface.

FIG. 7 illustrates a prior art procedure for handling interrupts in the execution of a conventional multitasking operating system. Elements in the FIGS. 7 and 8 are illustrated for simplicity and clarity and have not necessarily been drawn to scale. FIG. 7 illustrates the occurrence of interrupts from various sensors 120 (i.e., a pulse signal 704 from a GPS sensor 120), the handling of received interrupts by an interrupt hardware 702, device driver 404, operating system 414 and application 402. A single interrupt being handled in shown in FIG. 7 and briefly illustrates the interrupt handling issues commonly known to practitioners in the art. The actions illustrated FIG. 7 are performed approximately ten thousand times per second in conventional systems. This sequence diagram illustrates a mechanism to handle of the interrupt vector and any other information required for interrupt processing related to an update 720 of a single value in the state vector module 112. In this conventional implementation the application processor 106 is designed to perform data acquisition tasks that are frequent having substantially small data size, while performing large data movement and calculation tasks at a slower rate, The example illustrated in FIG. 7 is a small subset (just one non synchronous parameter) of a complete pattern of data acquisitions typically occurring in a moving machine vision system. Typical number of interrupts can easily reach hundreds of parameters, and ten thousand interrupts per second. Cache misses and thread conflicts for data reads and writes further complicate analysis and timing errors that lead to poorly performing systems. The OS 414/Memory controller objects 430 show the scheduling and memory movement aspects and randomness of the interrupt events. Another complicating aspect is OS's 414 mutex/semaphore conflict resolution mechanism that is application code dependent.

FIG. 8 illustrates a novel procedure for handling interrupts in the execution of a conventional multitasking operating system utilized by an integrated system for processing machine vision data on a mobile platform, in accordance with an embodiment of the present invention. In contrast to conventional mechanism illustrated in FIG. 7, this approach allows a plurality of sensors 120 to update data in the state vector module 112 without any involvement of the conventional interrupt handling routine in either push or pull mode. In either push or pull, a DATCC co-processor 110 handles the interface to a plurality of sensors 120 and may propagate updates originated from other sensors 120 via the state vector module 112. It is noted that operating system 414 may receive an interrupt 708 from an internal timer determining that application thread 402 needs to run on a nominal schedule. The application 402 may simply read/write a group of values from/to state vector module 112 using a non-blocking interface. This approach eliminates mutex and semaphore related issues and enables retrieving all requested data in a continuous block and with deterministic timing as the data is placed in register space by the state vector module 112. Advantageously, in this case, all tasks involved in interrupt handling such as but not limited to callbacks 712, context switches 716, etc. are performed just once and the entire content of the state vector is communicated to the application thread 402 at step 810. Thus, live monitoring and status management tasks are greatly simplified.

FIG. 9 illustrates a sequence diagram showing interactions between a state vector module and a plurality of co-processing components on a macro level, in accordance with an embodiment of the present invention. In one exemplary embodiment, an integrated system for processing machine vision data and performing active control of a mobile platform using state vector management includes a state vector module 112 communicatively coupled to a plurality of DATCC co-processors 110 a-c. FIG. 9 describes high level interactions of multiple DATCC co-processors 110 a-c with the state vector module 112 in the exemplary SOC. It should be noted that the described interactions are standardized through interfaces and concepts of operation described later. While for purposes of simplicity in illustration FIG. 9 depicts only interactions between the state vector module 112 and DATCC co-processors 110 a-c, interfaces to other co-processing components described above, such as, without limitation, DATCAP 206, motor controller 220, pointing 226, INS 228 and FPGA Interface 516, all work substantially similarly at the described macro level. For further convenience of description, the term “DATCALC” is used hereinafter to refer collectively to the calculation-related co-processing components, such as pointing 226, INS 228, etc. and the term “DATAPC” is used hereinafter to refer to DATA Producing and Consuming components, such as DATCC 110, DATCAP 206, DATCALC co-processors, Ethernet interface 330 and device drivers 404. Accordingly, in various embodiments, DATCC co-processors 110 a-c shown in FIG. 9 represents any combination of DATAPC or DATCALC instances.

According to an embodiment of the present invention, state vector module 112 performs repetitive operations at a tightly controlled but configurable rate. During normal operation, state vector module 112 periodically assumes an UPDATE state 910 that copies (asserts) a subset of its elements to all DATAPC components shown as DATCC 110 a-c in FIG. 9. In accordance with an embodiment of the present invention, each DATCC 110 maintains subsets of state vector elements stored in buffers 1012 and 1014 (shown in FIG. 10). The plurality of DATCC co-processors 110 includes a hardware logic configured to control the acquisition of the data which typically defines the data consumption interaction with the state vector module 112. Furthermore, the hardware logic of DATCC 110 maintains a corresponding map of state vector data elements to the subsets 1012 and 1014 defined for that particular DATAPC component. Advantageously, the design approach of one embodiment illustrated in FIG. 9 enables very rapid (substantially simultaneous) update 910 of the state vector data to each DATAPC component.

According to an embodiment of the present invention, state vector module 112 also periodically assumes a QUERY state 912, which may be triggered by a corresponding query timer 914 b shown in FIG. 9. The operation performed in this state comprises an inverse mapping of data from one of the DATCC components 110 to the state vector data elements controlled by the state vector component 112. It is noted that the assertion of data from the DATCC's 110 write buffer 1014 to the state vector module 112 defines the data producer role for that particular DATCC co-processor 110. It is further noted that state vector module 112 maintains the system wide map which associates each DATCC's 110 write subset buffer element 1014 to the state vector module 112. In other words, state vector module 112 supports a multiple-reader-single-writer version of the data structure. This multiple-reader-single-writer structure basically supports a broadcast paradigm: one data producer writes or broadcasts at one time and multiple data consumers receive the broadcast concurrently.

FIG. 9 shows a very typical state vector module 112 operation scenario that is illustrative of various features contemplated by various embodiments of the present invention. As described above, each DATCC 110 comprises a distinct electronic co-processing entity that performs a particular set of complex tasks. This is generally true for each DATAPC element. It is noted that each DATCC co-processor 110 a-c is preferably communicatively coupled to a different set of sensors from the plurality of sensors and/or different co-processing components. For example, first DATCC co-processor 110 a may be coupled to sensors 120 a providing inertial and positional data related to the mobile platform, such as but not limited to, gyroscopes, GPS devices and accelerometers; second DATCC co-processor 110 b may be coupled to a plurality of encoders 120 b; and third DATCC co-processor 110 c may be coupled to motor controller 220. In turn, motor controller 220 may be coupled to a plurality of additional physical components 902. Such physical components 902 may include without limitations torque command signals, a pulse width modulation (PWM) control system, limit switches, various devices that measure, for example, voltage, current and position of the system.

According to an embodiment of the present invention, generally, each DATCC co-processor 110 provides very reliable operation and very low internal jitter. However, in this heterogeneous mode of operation, each DATCC 110 a-c is subject to intrinsic jitter of the devices to which they are communicatively coupled to. In other words, each sensor/device 120 a-b, 220 and 902 is characterized by an intrinsic jitter. Accordingly, several jitter conditions illustrated with respect to embodiments described herein are for illustrative purposes only and are not meant to limit or otherwise narrow the scope of the present invention unless otherwise explicitly claimed.

First DATCC co-processor 110 a in FIG. 9 illustrates a data acquisition mode where a GPS device 120 a provides a time reference generally in a pulse per second (PPS) interval signal 704. However, the GPS device 120 a needs some time to calculate current position and this calculation time varies. Accordingly, in one embodiment of the present invention, first DATCC co-processor 110 a traps and time stamps the PPS signal 704 then promptly queries 904 the gyroscopes and accelerometers 120 a. First DATCC co-processor 110 a receives a corresponding measurement from the GPS device 120 a after it finishes calculating the GPS position. This data acquisition mode comprises a hybrid push pull mechanism implemented by the first DATCC co-processor 110 a shown in FIG. 9.

Simultaneously, second DATCC co-processor 110 b ingests bit streams of data provided by angular encoders 120 b. The data ingesting operation 906 is driven by the encoder timing from the encoder device 120 b. Thus, second DATCC co-processor 110 b is also subject to jitter, in this case directly dependent on encoder's 120 b output. This is an example of push only data transfer mechanism implemented by the second DATCC co-processor 110 b.

Yet another simultaneous data acquisition mode is illustrated by the third DATCC co-processor 110 c in FIG. 9. The third DATCC co-processor 110 c queries a complex external or internal motor control module 220 that is performing high rate measurements and calculations for low level motor control. The DATACC 110 c system then queries the state of the mobile platform on its own timer utilizing a pull only model. In response to receiving a subset of the state vector data, third DATCC co-processor 110 c rapidly sets 909 the torque command parameters using data received form the state vector module 112. This is an example of a flexible multirate push pull data transfer model implemented by the third DATCC co-processor 110 c.

Thus, advantageously, according to various embodiments of the present invention, the state vector module 112 is capable of supporting multiple co-processing components performing calculations that are nondeterministic and/or run at different rates. FIG. 9 illustrates an inherent capability to parallelize the data capture, collection and processing mechanism in various control systems and efficiently distribute and gather the state vector data elements from various data producing and consuming components of the system. It is noted that queries or updates of state vector information may be scheduled on any regular or irregular time basis. Equivalently, state vector updates may be shared between DATCC co-processors 910 a-c in real time (or near real time) substantially in-parallel as changes are made to the state vector data.

FIG. 10 is a system diagram illustrating a state vector module in accordance with an embodiment of the present invention. In one embodiment, state vector module 112 controls read-write operations upon state vector data in BRAM memory 526. As described above, the state vector module 112 periodically updates various DATAPC entities (i.e., DATCC 110 a-c) with the “newest” and complete set of state vector data. Data structures that are not highly concurrent commonly require the use of a lock at the top of the data structure to serialize access to the data structure. The overhead of lock usage is significant, especially when multiple, simultaneous attempts at data-structure access make the lock a hot spot of contention. In addition, in mobile platform systems, the ability to store and read a complete set of parameter measurements that represent the entire state of the system at a particular time instance is highly desirable. For example, merely reading the latest values provided by gyroscope sensors 120 a without reading the latest accelerometer values (e.g., because they have not been updated yet) typically results in poor behavior of the system. In addition, a variety of metastable conditions can occur while state vector module's 112 interfaces communicate with various data producing and consuming components.

To eliminate the aforementioned concerns various embodiments of the state vector module 112 utilize a triple buffered approach of on chip memory for storing the state vector data elements. In one embodiment, each buffer represents one of the three conditions of the state vector data. In accordance with the embodiment, state vector module 112 designates the first buffer (e.g., state vector A 112 a) as a read buffer, third buffer (e.g., state vector C 112 c) as a write buffer and reserves a second buffer (e.g., state vector B 112 b) for a future write operation. It is noted that the memory address of the first buffer 112 a is assigned to a read pointer of a read pointer controller 1004, address of the third buffer 112 c is assigned to a write pointer of a write pointer controller 1002 and address of the second buffer 112 b is assigned to a next pointer (not shown in FIG. 10). In this embodiment, each pointer comprises a hardware index “pointer” used to directly manipulate memory. Advantageously, state vector module 112 utilizes the three memory buffers 112 a-c to perform read-write operations in a highly parallel fashion.

According to an embodiment of the present invention, the state management logic of the state vector module 112 further comprises a reading and writing mechanism circuitry connecting the aforementioned buffers 112 a-c with DATCC co-processors 110. According to an embodiment of the present invention, the writing mechanism circuitry runs asynchronously from the reading mechanism circuitry. In other words, this approach utilizing two separate communication buses, such as a reading mechanism bus 1016 and writing mechanism bus 1018 simplifies timing rules and timing constraints and simplifies analysis for eliminating meta-stability related problems.

Due to well-segregated reading and writing mechanism circuitry the workflow of the read and write cycles can be substantially separated and discussed independently herein. The state management logic of the state vector module 112 begins the read cycle (operation) by retrieving data from the buffer pointed to by the read pointer 1004 (in this case, first buffer 112 a). In other words, the read pointer 1004 selects the first buffer 112 a as denoted by a component 1005. In accordance with an embodiment of the present invention, each DATCC co-processor 110 maintains their own subsets 1012 and 1014 of state vector data. As illustrated in FIG. 10, the reading mechanism bus 1016 comprises a communications bus that connects the state vector module's designated read buffer 112 a with corresponding local reading buffers 1012 at each DATCC co-processor 110 containing subsets of state vector data relevant for each particular DATCC co-processor 110. In various embodiments, the reading mechanism bus 1016 may comprise a conventional wired bus or faster serial encoded bit stream circuit that is connected to all DATCC co-processors 110. In most embodiments, since the state vector data has a fixed and unitary nature and typically not very large in size (e.g., 100 kbits is a fairly large state vector), a fast serial connection to all DATCC's 110 can be more efficient. Thus, in such embodiments, the state management logic of the state vector module 112 transmits (broadcasts) a serial stream of the entire content of the first buffer 112 a at once and this stream is available to all of the DATCCs 110 at once due to the state vector memory designed to be both multi-ported and non-blocking.

According to an embodiment of the present invention, upon receiving the broadcasted state vector data, each DATCC 110 may utilize a read table defined at the embedded system level to decode the serial communications and populate the local read buffers (SUBSV) 1012. It is noted that in various embodiments, this read table may be hardwired or may comprise a simple lookup memory. Additional considerations regarding the coordination required for this reading mechanism to work properly are discussed below in conjunction with FIG. 11. Once a complete set of all of the state vector elements is delivered to the reading bus 1016, the state control logic completes the read operation by changing the read pointer controller 1004 to point to the last state vector module buffer pointed to by the write pointer controller 1002 (i.e., third buffer 112 c).

In accordance with an embodiment of the present invention, the state management logic further includes the aforementioned write pointer controller 1002 enabled to control the writing mechanism circuitry for writing state vector data from a DATCC co-processor to one of the three state vector module buffers 112 a-c.

To begin the operation, the write pointer controller 1002 selects a buffer that is not being written to and that contains the oldest complete state vector data set. In FIG. 10 the second buffer 112 b illustrates such buffer. This operation is referred to hereinafter as latching the write pointer 1114 and happens when a query cycle 912 starts (shown in FIG. 11). In accordance with an embodiment of the present invention, in response to receiving a query cycle start signal 914 b (shown in FIG. 9) the write pointer controller 1002 access a memory location containing a write map and processes this write map. In one embodiment, the write map describes each DATCC entity 110 as well as identifies locations of local write buffers 1014 at each DATCC 110 source as well as state vector element destinations. In accordance with an embodiment of the present invention, state vector module 112 also utilizes a set of flags corresponding to each DATCC co-processor 110. In one embodiment, these flags include a copy flag 1006, a query flag 1008 and a valid flag 1010.

Next, the write pointer controller 1002 sets the query flag 1008 and reads a valid flag 1010 to verify that the writing DATCC 110 has asserted a correct complete data subset to its local write buffer 1014. If the write pointer controller 1002 determines that the valid flag 1010 is set then it utilizes the writing mechanism bus 1018 to move data from the writing DATCC 110 to the write buffer (i.e., third buffer 112 c) pointed to by the write pointer controller 1002. In various embodiments, similarly to the reading mechanism bus 1016, the writing mechanism bus 1018 may comprise a conventional wired bus or faster serial encoded bit stream circuit that is connected to all DATCC co-processors 110. Advantageously, the writing mechanism described herein substantially guarantees scalable data transfers with respect to the size of the state vector data elements.

FIG. 11 illustrates an expanded sequence diagram view showing steps performed during read and write operations, in accordance with an embodiment of the present invention. As previously indicated, state vector management module 112 periodically receives an update cycle signal 910 initiated by the first trigger mechanism 914 a in order to update all DATCC co-processors 110 with the latest information stored in the read buffer of state vector module 112 so that each DATCC co-processor 110 a-c has a current and accurate copy of the state vector information. As part of this update process, at step 1104, the read pointer controller 1004 latches its read pointer to point to the buffer containing the most recent complete state vector data (i.e., read buffer 112 a) in a one clock cycle atomic operation. At step 1106, read pointer controller 1004 generates high level signals for copy flags 1006 associated with each DATCC co-processor 110 indicating that update operation is being performed. In some embodiments, copy flag 1006 may get asserted for each element in local state vector read buffer 1012 that DATCC co-processor 110 gets a copy of. Next, at step 1108, read pointer controller 1004 broadcasts values of all state vector elements stored in first buffer 112 a of the state vector module via the reading bus 1016 described above to all local read buffers 1012 of all DATCCs 110. Once the broadcast is complete, at step 1110, the read pointer controller 1004 resets copy flags 1006 with each DATCC co-processor 110 by generating a corresponding low level signal. As previously indicated, in some embodiments, copy flag 1006 can be set/reset for each state vector element being copied.

During normal operation, at a certain point, each DATCC co-processor 110 writes one or more state vector data element values back to state vector memory 112. For example, third DATCC co-processor 110 c (shown in FIG. 9) may periodically receive from motor controller 220 various state vector data, such as, but not limited to, position, voltage and current measurements. According to an embodiment of the present invention, once DATCC co-processor 110 is ready to write its subset of state vector data element values back to the state vector module 112 it sets its valid flag 1010.

As previously indicated, in one embodiment, state vector module 112 may utilize a timer 914 b to periodically trigger, at a predetermined interval relative to the latest update 910 operation, a process to query 912 DATCC co-processors 110 in order to extract subset of the state vector information ready for writing. As part of a query process 912, at step 1114, the write pointer controller 1002 latches the address of the write buffer (denoted in FIG. 10 as third buffer 112 c) in a one clock cycle atomic operation. At step 1116, the write pointer controller 1002 traverses the write table and generates high level signals for query flag 1008 indicating that query operation 912 is being performed and selects a particular DATCC co-processor 110 to query. Next, at step 1118, the write pointer controller 1002 determines whether the valid flag 1010 is set for the selected DATCC co-processor 110. In response to determining that the valid flag 1010 is set for the selected DATCC co-processor 110, at step 1120, write pointer controller 1002 transfers data stored in the local write buffer 1014 of the selected DATCC 110 via the writing mechanism bus 1018 to the buffer serving as a write buffer of the state vector module 112, such as the third buffer 112 c. According to an embodiment of the present invention, DATCC co-processors 110 can write data to the state vector memory 112 one at a time. Thus, during the query operation write pointer controller 1002 repeats steps 1118-1120 for each DATCC co-processor 110. In other words, each DATCC co-processor gets a chance to write its state vector data subset (if it has any new data) before the completion of the query operation 912.

According to an embodiment of the present invention, once the third buffer 112 c gets updated with the latest data from all DATCC co-processors 110, at steps 1122 and 1126, the control logic of the state vector module 112 updates the write pointer controller 1002 and read pointer controller 1004, respectively, so that the read pointer controller 1004 is now pointing to the third buffer 112 c, while the write pointer controller 1002 now points to the second buffer 112 b. It is noted that once the third buffer 112 c is designated as a read buffer and the second buffer 112 b is designated as a write buffer, the state vector module 112 reserves the first buffer 112 a for a future write operation. As shown in FIG. 11, at step 1124, state vector module 112 resets query flag back to low indicating completion of the query operation 912 for that particular DATCC 110.

Various embodiments described above are directed to a machine vision system attached to a mobile platform. The system comprises co-processing elements that are configured to acquire and assert data, offload data movement and computational tasks from system's application processor(s). The system further includes a state vector module containing a plurality of addressable memory locations (buffers) that are used for state vector parameter storage and a state management logic communicatively coupled to the state vector memory and the multi-core computer processor and configured to provide read and write control to the state vector memory. Advantageously, in an embodiment, the disclosed state management logic includes both a read pointer controller and a write pointer controller and further includes hardware elements by which the read and write pointer controllers exchange information with the co-processing elements in a safe manner. The novel implementation of the state vector update, control and operating principles substantially guarantee the consistency of the state vector data using a fast, low latency and low jitter approach.

The techniques described herein are exemplary, and should not be construed as implying any particular limitation of the certain illustrated embodiments. It should be understood that various alternatives, combinations and modifications could be devised by those skilled in the art. For example, steps associated with the processes described herein can be performed in any order, unless otherwise specified or dictated by the steps themselves. The present disclosure is intended to embrace all such alternatives, modifications and variances that fall within the scope of the appended claims.

The terms “comprises” or “comprising” are to be interpreted as specifying the presence of the stated features, integers, steps or components, but not precluding the presence of one or more other features, integers, steps or components or groups thereof.

Although the systems and methods of the subject invention have been described with respect to the embodiments disclosed above, those skilled in the art will readily appreciate that changes and modifications may be made thereto without departing from the spirit and scope of the certain illustrated embodiments as defined by the appended claims. 

What is claimed is:
 1. An integrated state vector management system for control systems comprising: a plurality of co-processors configured to generate and utilize state vector data; and a state vector module communicatively connected to each of the plurality of co-processors, wherein the state vector module comprises: a state vector memory comprising at least three memory buffers for storing three datasets of state vector data; and a state vector memory control logic communicatively coupled to the state vector memory, the state vector control logic configured to provide read and write control to the state vector memory, the state vector memory control logic comprising at least a write pointer controller and a read pointer controller.
 2. The integrated system of claim 1, wherein a first memory buffer of the at least three memory buffers comprises a read buffer, a second memory buffer of the at least three memory buffers comprises a write buffer and a third buffer of the at least three memory buffers is reserved for a future write operation.
 3. The integrated system of claim 2, wherein the state vector module is communicatively connected to each of the plurality of co-processors via two separate communication buses including a write bus and a read bus.
 4. The integrated system of claim 3, wherein the write bus and the read bus comprise a serial encoded bit stream circuit.
 5. The integrated system of claim 4, wherein the read pointer controller is configured to read entire dataset of the state vector data from the read buffer and to broadcast the entire dataset of the state vector data via the read bus to each of the plurality of co-processors substantially simultaneously after a pre-determined period of time.
 6. The integrated system of claim 1, wherein each of the plurality of co-processors is configured to maintain at least a copy flag, a query flag and a valid flag utilized by the read pointer controller and write pointer controller during read and write operations.
 7. The integrated system of claim 4, wherein each of the plurality of co-processors is configured to maintain at least a first and second subsets of the state vector data wherein the first subset is stored in a local read buffer and the second subset is stored in a local write buffer of the corresponding co-processor and wherein the local write buffer is connected to the write bus and the local read buffer is connected to the read bus.
 8. The integrated system of claim 7, wherein the state vector module is configured to determine, after a predefined period of time, whether any of the plurality of co-processors contains a new subset of the state vector data in its local write buffer to write to the state vector memory and configured to, in response to identifying one or more co-processors ready to write the new subset of the state vector data, progressively select each of the plurality of co-processors for a write operation.
 9. The integrated system of claim 1, wherein the plurality of coprocessors and the state vector module comprises at least one of an Application Specific Integrated Circuit (ASIC) and a Field Programmable Gate Array (FPGA).
 10. The integrated system of claim 8, wherein the write operation comprises transmitting a subset of the state vector data from the local write buffer of the selected co-processor to the write buffer of the state vector module via the write bus.
 11. An integrated state vector management system for control systems comprising: a plurality of sensors configured to acquire state vector data; a plurality of co-processors communicatively coupled to the plurality of sensors, the plurality of co-processors including a hardware logic configured to control the acquisition of the state vector data and configured to analyze the state vector data; and a state vector module communicatively connected to each of the plurality of co-processors, wherein the state vector module comprises: a state vector memory comprising at least three memory buffers for storing three datasets of state vector data; and a state vector memory control logic communicatively coupled to the state vector memory, the state vector control logic configured to provide read and write control to the state vector memory, the state vector memory control logic comprising at least a write pointer controller and a read pointer controller.
 12. The integrated system of claim 11, wherein the state vector memory control logic provides read and write control to the state vector memory in a non-blocking manner.
 13. The integrated system of claim 11, wherein the state vector memory stores a plurality of state vector data values utilized by the plurality of co-processors.
 14. The integrated system of claim 11, wherein the plurality of coprocessors and the state vector module comprises at least one of an Application Specific Integrated Circuit (ASIC) and a Field Programmable Gate Array (FPGA).
 15. The integrated system of claim 11, wherein the state vector module is communicatively connected to each of the plurality of co-processors via two separate communication buses including a write bus and a read bus. 